|
Algorithms said to employ a Ping-Pong scheme exist in different fields of Software Engineering. They are characterized by an alternation between two entities. In the examples described below, these entities are communication partners, network paths or file blocks. ==Databases== In most database management systems durable database transactions are supported through a log file. However, multiple writes to the same page of that file can produce a slim chance of data loss. Assuming for simplicity that the log file is organized in pages whose size matches the block size of its underlying medium, the following problem can occur: If the very last page of the log file is only partially filled with data and has to be written to permanent storage in this state, the very same page will have to be overwritten during the next write operation. If a crash happens during that later write operation, previously stored log data may be lost. The Ping-Pong scheme described in eliminates this problem by alternatingly writing the contents of said (logical) last page to two different physical pages inside the log file (the actual last page ''i'' and its empty successor ''i+1''). Once said logical log page is no longer the last page (i.e. it is completely filled with log data), it is written one last time to the regular physical position (''i'') inside the log file. This scheme requires the usage of time stamps for each page in order to distinguish the most recent version of the logical last page one from its predecessor. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Ping-pong scheme」の詳細全文を読む スポンサード リンク
|